3. Merchant Integration Flow: Card Tokenisation and Tokenised Payments

3.2.6 Tokenised Card Payment: Step 4 – Asynchronous Payment Request Response

3.2.6.1 Payment Request Response API Response

After submitting the tokenised payment request, a response indicating whether that request was successfully received,
or not; is sent back to the merchant.
Take note, this is a lengthy batch process and runs as scheduled tasks between VFS and the bank.
It should never be relied upon to be returned quickly or included in a synchronous user–journey with the customer.
See 4.6 Appendix F: Tokenised Payment Error Codes.

Figure 19. Tokenised Payment: Step 4 – Payment Request Response Post-Back

3.2.6.2 Recurring Payment API Post Fields

Table 19. Tokenised Payment: Step 4 – Payment Request Response Fields
# Field
(Case–Sensitive)		 Required
Mandatory
Optional		 Type Length Description
1. WasSuccessful M String "true" if tokenised recurring payment request was successfully received by the bank, "false" otherwise.
2. Message O String Friendly display field if errors occur (not needed)
3. Error.ErrorCode M String Error code if any (00 and blank are successes) See 4.6 Appendix F: Tokenised Payment Error Codes.
4. Error.ErrorDescription M String Error code if any (00 and blank are successes) See 4.6 Appendix F: Tokenised Payment Error Codes.
5. Exception.Message M String C# Exception Object (this shouldn't be populated)
6. Exception.Source M String C# Exception Object (this shouldn't be populated).
7. Exception.StackTrace M String C# Exception Object (this shouldn't be populated)
8. Exception.InnerException M String C# Exception Object (this shouldn't be populated)

Continue

Return